Plugin API

AWeb can handle many types of files internally, or with the use of datatypes. The operation of AWeb may be extended by use of external plugin modules. Such a plugin module would handle files that AWeb can't handle itself, or it would offer more functionality than AWeb does.

Plugin modules must not be confused with external ARexx scripts, historically also called "plugins". A plugin module is a shared library with a specific interface. Plugin modules are allowed to render directly into the AWeb window, either as a standalone object, or as an embedded object in a HTML document.

The API (Application Programmers Interface) is freely available. The archive contains all documentation, C header files, and an example plugin module with source (written in C).

Note: If you download the API, and start programming a plugin, please let me know. I like to have some idea of what is going on, and maybe do some coordination (we don't need 27 people working on a similar plugin...).

Download the archive from http://www.xs4all.nl/~yrozijn/aweb/awebapi.lha (129kB)
Last modified: 18-Oct-1999 (API version 2.0).

Overview of changes

Version 2.0 (18-Oct-1999):
This API corresponds with AWeb 3.3.
Added a way to send commands to the plugin through the AWeb ARexx interface.
Added a way to execute AWeb ARexx commands from within the plugin.
Introduced a new plugin type, that can filter incoming data before it is handled by the internal HTML parser.
Version 1.6 (4-Aug-1997):
Added two attributes to be set in image decoders, to allow the correct execution of JavaScript onLoad event handlers (to be introduced in AWeb 3.1).

Back to AWeb Home Page